Everything Totally Explained


Ask & we'll explain, totally!
Framing (World Wide Web)
Totally Explained


  NEW! All the latest news in the worlds of computer gaming, entertainment, the environment,  
finance, health, politics, science, stocks & shares, technology and much, much, more.  


View this entry using RSS

Everything about Framing World Wide Web totally explained

On a web page, framing means that a website can be organized into frames. Each frame displays a different HTML document. Headers and sidebar menus don't move when the content frame is scrolled up and down. For developers frames can also be convenient. For example, if an item needs to be added to the sidebar menu, only one file needs to be changed, whereas each individual page on a non-frameset website would have to be edited if the sidebar menu appeared on all of them. However, server-side includes and scripting languages such as PHP can also be used to accomplish this aim without some of the drawbacks of frames such as confusing the operation of the address bar and back and forward buttons.

History

Netscape 2.0 introduced the elements used for frames in the 1990s (see Netscape Navigator). At that time, Netscape proposed frames to the W3C for inclusion in the HTML 3.0 standard.

Syntax

The frameset replaces the <body> and </body> tags, and describes the dimensions (in percentages) of the frames. These percentages should add to 100, though the last one may be replaced with an asterisk as a shortcut to the remaining screen space. Within the frameset, the framed panels are described with their source documents. The element may be included so browsers with frames disabled (or browsers that don't support frames) can display something to the user, as in this example:<br> &lt;frameset cols="85%, 15%"&gt; &lt;frame src="URL OF FRAME PAGE 1 HERE"&gt; &lt;frame src="URL OF FRAME PAGE 2 HERE"&gt; &lt;noframes&gt; Text to be displayed in browsers that don't support frames &lt;/noframes&gt; &lt;/frameset&gt; <h2> Content Sources </h2> The contents of the frames may be hosted on the same <a href=http://Server__computing.totallyexplained.com title="Server (computing) - Totally Explained">server</a> as the parent page, or it may link in code from another website server such that these external contents are automatically displayed within the frame (<a href=http://transclusion.totallyexplained.com title="transclusion - Totally Explained">transclusion</a> or <i>remote loading</i>). This may be confusing and inconvenient to the users: they can get the impression that the information belongs to the same website; also, less than the full browser window is available and the address bar is less informative. Some websites request not to be used in this way on other websites; some discourage it by including a <a href=http://framekiller.totallyexplained.com title="framekiller - Totally Explained">framekiller</a> script in its pages. The framing website runs a risk of being blamed for external content that, for example, is or becomes inaccurate or objectionable. In addition, there may be legal issues associated with framing, in that the owner of the external content may object to the involuntary (and possibly objectionable) implied association with the framing website. Visitors may confuse ownership of copyrights or trademarks of the external site with the owner of the framing site. <h2> Criticism </h2> Chief criticism of the practice of framing HTML content includes:<br> <ul><li> That framing breaks the link between content and a URL, making it difficult to link to or bookmark a particular item of content within the frameset <li> That the implementation of frames is inconsistent across different browsers <li> That framing confuses the boundaries between content on different servers, which raises issues of copyright infringement <li> That visitors arriving from search engines may land on a page intended for display in a frame, which often has no navigation <li> That frames change the behavior of the back button <li> That frames usually don't print the way users expect they will</ul></ol></ul></ol></ul></ol></ul></ol></ul></ol></ul></ol></ul> <h2> Replacements </h2> Although frames were included in the <a href=http://XHTML.totallyexplained.com title="XHTML - Totally Explained">XHTML</a> 1.0 specification, they were not carried across to XHTML 1.1. The intended eventual replacement is <a href=http://XFrames.totallyexplained.com title="XFrames - Totally Explained">XFrames</a>, which attempts to solve the problem of addressing a populated frameset through composite URIs. For those serving web content under the XHTML 1.0 specification, documents may be embedded within one another via either the <code>object</code> or <code>iframe</code> element tags. Under the 1.1 specification, <code><a href=http://iframe.totallyexplained.com title="iframe - Totally Explained">iframe</a></code> was removed, leaving only the <code>object</code> element for transclusion until browsers begin support for XFrames. Unfortunately, Internet Explorer 7 doesn't handle <code>object</code>s used to replace the function of an <code><a href=http://iframe.totallyexplained.com title="iframe - Totally Explained">iframe</a></code>, it doesn't recognize that a link from within the included page has the containing page as its <code>_parent</code>. Therefore constructing a menu to be included on every page, in imitation of a <code>frameset</code>, fails as the parent frame can't be targeted. <a href=http://KHTML.totallyexplained.com title="KHTML - Totally Explained">KHTML</a> and <a href=http://Gecko.totallyexplained.com title="Gecko - Totally Explained">Gecko</a> based browsers, like <a href=http://Konqueror.totallyexplained.com title="Konqueror - Totally Explained">Konqueror</a>, <a href=http://Safari__web_browser.totallyexplained.com title="Safari (web browser) - Totally Explained">Safari</a> and <a href=http://Firefox.totallyexplained.com title="Firefox - Totally Explained">Firefox</a>, however, work perfectly well with this construct.<br> &nbsp;&nbsp;&nbsp;Frames are removed in the HTML5 draft, citing usability concerns.<br> <p><font size=4><b>Further Information</b></font><p> <a href="http://eclgy.com/Framing World Wide Web">Get more info on 'Framing World Wide Web'</a>.<p><br> <center><table width=80% border=0 cellpadding=5 cellspacing=0 bgcolor=#f4f4f4 style="border-style:dotted; border-collapse:collapse; border-width:thin"><tr><td><font face=verdana size=2> <font size=4><b>External Link Exchanges</b></font><p> <font size=1><p align=justify>Do you know how hard it&nbsp;is to get a link from a large encyclopaedia? Well we're different and will prove it. To get a link from us just add the following HTML to your site on a relevant page: <ul> <b><tt>&lt;a href="http://framing__world_wide_web.totallyexplained.com"&gt;Framing (World Wide Web) Totally Explained&lt;/a&gt;</tt></b> </ul> <p align=justify>Then simply click through this link from your web page. Our crawlers will verify your link, extract the title of your web page and instantly add a link back to it. If you like you can remove the words <i>Totally Explained</i> and embed the link in article text.<br> &nbsp;&nbsp;&nbsp;As long as your link remains in place, we'll keep our link to you right here. Please play fair - our crawlers are watching. Your site must be closely related to this one's topic. Any kind of spamming, dubious practises or removing the link will result in your link from us being dropped and, potentially, your whole site being banned. </font></td></tr></table></center><br><br> <center><script> google_ad_client = "pub-2573932102663475"; google_ad_width = 728; google_ad_height = 90; google_ad_format = "728x90_as"; google_ad_type = "text"; google_ad_channel = "6827908563"; google_color_border = "ffffff"; google_color_bg = "ffffff"; google_color_link = "4444aa"; google_color_text = "000000"; google_color_url = "646464"; </script><script src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script><p></div> <table width=100% border=1 cellpadding=0 cellspacing=0 bgcolor=#f4f4f4 style="margin-top:4px; margin-bottom:4px; border-collapse:collapse; border-width:thin"><tr><td align=center><font size=1 face=verdana> Copyright &copy; 2007-8 <a href=http://totallyexplained.com>totallyexplained.com</a> | Licensed under the <a href=http://totallyexplained.com/gfdl.htm>GNU Free Documentation License</a> | <a href=http://totallyexplained.com/articles.htm>Site Map</a><br>This article contains text from the Wikipedia article <a href="http://en.wikipedia.org/wiki/Framing (World Wide Web)">Framing (World Wide Web)</a> (<a href="http://en.wikipedia.org/w/index.php?title=Framing (World Wide Web)&action=history">History</a>) and is released under the <a href=http://totallyexplained.com/gfdl.htm>GFDL</a> | <a href=http://totallyexplained.com/display.php?q=framing__world_wide_web&rss=1>RSS Version</a></td></tr></table> </td></tr></table></td></tr></table> <script type="text/javascript"> var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www."); document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E")); </script> <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-1065688-2"); pageTracker._trackPageview(); </script>